home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.cbm
- Path: nntp.coast.net!torn!news!a10
- From: a10@server.uwindsor.ca (Darren Fuerst)
- Subject: Re: Problems with C64
- X-Nntp-Posting-Host: server.uwindsor.ca
- Message-ID: <Do340q.1Lt@news.uwindsor.ca>
- Sender: news@news.uwindsor.ca (Usenet)
- Organization: University of Windsor, Ontario, Canada
- References: <4hhkhe$b1s@morgan.vf.mmc.com> <4hr4do$jv4@dfw-ixnews1.ix.netcom.com> <4hs114$11q@ns1.thpl.lib.fl.us>
- Date: Mon, 11 Mar 1996 03:50:50 GMT
-
- In article <4hs114$11q@ns1.thpl.lib.fl.us> sfxu@scfn.thpl.lib.fl.us (Jayme Rice) writes:
- >characters most times, it is one of the RAM memory chips that when out.
- >To replace the bad one, it's a hit and miss deal. You have to replace
- >one and see if it corrects the problem. If it doesn't, then you replace
- >the second and so on. A big pain. The best way to approach the problem
-
- If you're going to replace the RAM, I'd just desolder all the old chips,
- solder in sockets, and fill 'em up with RAM known to be good (voice of
- experience here). If your 64 uses 4164's, you can also use 41256's
- (again, voice of experience). 41256's are very cheap and very plentiful.
- These are common in most older PC's (PC's, XT's, AT's). Most of these
- machines have long since been retired, so if you look hard you can probably
- find a "donor" sitting in a closet or storage room at work or at school
- (you guessed it, voice of experience -- I've got about 4 meg of these puppies
- kicking around).
-
- Darren
-
-
-